extra/qemu: to make qemu installable for aarch64 #1959
Conversation
Currently qemu package group has its problems, making it almost impossible to run libvirt with qemu: - qemu-user-static build will fail using native tool chain This will prevent the whole package, including qemu-system-* which can compile without any problem. - qemu-base and qemu-desktop depends on qemu-system-x86 Which makes completely no sense. This is something from the Archlinux PKGBUILD. - No way to install qemu-system-aarch64 As it has hard dependency on edk2-armvirt, which is not buildable yet natively on aarch64 (missing arm toolchain AFAIK). This update will solve the problems by: - Split qemu-user-static into its own PKGBUILD Qemu-user-statis has a completely different use-case compared to system emulators. The most common usage is allowing the host to chroot into rootfs for another arch. Thus it is not suitable to contain qemu-user-static into qemu package. There is already a feature request to upstream Archlinux: https://bugs.archlinux.org/task/76556 - Make qemu-base and qemu-desktop to change its default system emulator dependecy Now the PKGBUILD will choose the default system emulator depending on the target arch. - Make edk2-armvirt as optional dependency In fact we can directly install the same package from upstream Archlinux, as that package is just the edk2 uefi firmware, which is arch independent. Have tested qemu PKGBUILD natively on both x86_64 and aarch64, and resulted qemu can work with libvirt using KVM. Signed-off-by: Qu Wenruo <[email protected]>
|
does not compile qemu-user-static |
|
@Rippanda12 Static build failure is the reason to split that package out. And I have already mentioned, I only care about the qemu-system-* for now. Feel free if you can fix the static part. |
|
Another thing is, there isn't much usage for Firstly, While under most cases, aarch64 is the weaker target, thus we want The only exception is Apple M1, where Asahi Linux users may want |
|
For the static build failure, it's in fact the problem of the glibc package. In fact the newer glibc should be compiled with |
|
Seems some of these changes where added recently: |
Currently qemu package group has its problems, making it almost impossible to run libvirt with qemu:
qemu-user-static build will fail using native tool chain This will prevent the whole package, including qemu-system-* which can compile without any problem.
qemu-base and qemu-desktop depends on qemu-system-x86 Which makes completely no sense. This is something from the Archlinux PKGBUILD.
No way to install qemu-system-aarch64 As it has hard dependency on edk2-armvirt, which is not buildable yet natively on aarch64 (missing arm toolchain AFAIK).
This update will solve the problems by:
Split qemu-user-static into its own PKGBUILD Qemu-user-statis has a completely different use-case compared to system emulators. The most common usage is allowing the host to chroot into rootfs for another arch.
Thus it is not suitable to contain qemu-user-static into qemu package. There is already a feature request to upstream Archlinux: https://bugs.archlinux.org/task/76556
Make qemu-base and qemu-desktop to change its default system emulator dependecy Now the PKGBUILD will choose the default system emulator depending on the target arch.
Make edk2-armvirt as optional dependency In fact we can directly install the same package from upstream Archlinux, as that package is just the edk2 uefi firmware, which is arch independent.
Have tested qemu PKGBUILD natively on both x86_64 and aarch64, and resulted qemu can work with libvirt using KVM.
Signed-off-by: Qu Wenruo [email protected]